Triple
T31126521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marc-Antoine |
E793370
|
entity |
| Predicate | componentMarcOrigin |
P137413
|
FINISHED |
| Object | Latin Marcus |
—
|
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: Latin Marcus | Statement: [Marc-Antoine, componentMarcOrigin, Latin Marcus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentMarcOrigin Context triple: [Marc-Antoine, componentMarcOrigin, Latin Marcus]
-
A.
cargoOrigin
Indicates that a specified location is the starting point from which the cargo was initially shipped or dispatched.
-
B.
machineOrigin
Indicates that one entity is the source, creator, or place of manufacture for a machine-related entity.
-
C.
causeOfOrigin
Indicates that one entity is the source or initiating cause from which another entity originates or comes into existence.
-
D.
countryOfOrigin
Indicates the country from which an entity originally comes or was first produced, created, or established.
-
E.
describesOriginOf
chosen
Indicates that one entity specifies or explains the source, provenance, or origin 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 29, 2026, 9:05 p.m.