Triple
T31083680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serial Shipping Container Code |
E792170
|
entity |
| Predicate | hasApplicationIdentifier |
P1285
|
FINISHED |
| Object | 00 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 00 | Statement: [Serial Shipping Container Code, hasApplicationIdentifier, 00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApplicationIdentifier Context triple: [Serial Shipping Container Code, hasApplicationIdentifier, 00]
-
A.
hasApplicationType
Indicates that an entity is associated with or classified by a specific type or category of application.
-
B.
hasIdentifierSystem
chosen
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
-
C.
hasCommunicationIdentifier
Indicates that an entity is associated with a specific communication-related identifier (such as a phone number, email address, or messaging handle) used for contact or messaging purposes.
-
D.
haveIdentifier
Indicates that an entity is associated with a specific identifier used to uniquely reference or distinguish it.
-
E.
hasApp
Indicates that an entity possesses, provides, or is associated with a particular application.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 29, 2026, 9:02 p.m.