Triple
T33186484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electronic Product Code |
E849483
|
entity |
| Predicate | typicallyEncodedIn |
P201340
|
FINISHED |
| Object | RFID tags |
—
|
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: RFID tags | Statement: [Electronic Product Code, typicallyEncodedIn, RFID tags]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyEncodedIn Context triple: [Electronic Product Code, typicallyEncodedIn, RFID tags]
-
A.
encodedIn
Indicates that one entity is represented, stored, or expressed within another entity using a specific encoding or format.
-
B.
notEncodedIn
Indicates that a piece of information, data, or content is explicitly absent from or not represented within a given encoding, format, or medium.
-
C.
typicalEncoding
chosen
Indicates that one entity serves as the standard or most common encoding or representation format used for another entity.
-
D.
encodes
Indicates that one entity contains or represents the information, instructions, or structure of another in a coded or symbolic form.
-
E.
encodingIs
Indicates that one entity serves as the specific encoding or coded representation of another entity.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:29 a.m.