Triple
T32616184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlie Tango |
E833790
|
entity |
| Predicate | registrationMark |
P175013
|
FINISHED |
| Object | Charlie Tango |
—
|
NE NERFINISHED |
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: Charlie Tango | Statement: [Charlie Tango, registrationMark, Charlie Tango]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registrationMark Context triple: [Charlie Tango, registrationMark, Charlie Tango]
-
A.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
-
B.
marker
Indicates a relationship where one entity serves as a sign, label, or indicator that identifies, distinguishes, or signals a property or status of another entity.
-
C.
reportedMarks
Indicates that an entity has formally communicated or submitted the marks/grades of another entity (such as a student or assessment) to a relevant party or system.
-
D.
distinctiveMarking
Indicates that one entity bears a unique or distinguishing visual feature or pattern that sets it apart from others.
-
E.
marque
Indicates that one entity is the brand or make associated with another entity, such as a product, vehicle, or manufactured item.
- F. None of above. chosen
Provenance (4 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd9bae8c8190b528641499162a75 |
completed | May 3, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cd119cac8190a0b3ebe8b9c742c2 |
completed | May 3, 2026, 4:20 a.m. |
Created at: May 1, 2026, 1:06 a.m.