Triple
T8451523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .yt |
E199809
|
entity |
| Predicate | administrativeRelationship |
P37165
|
FINISHED |
| Object | overseas department of France |
—
|
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: overseas department of France | Statement: [.yt, administrativeRelationship, overseas department of France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeRelationship Context triple: [.yt, administrativeRelationship, overseas department of France]
-
A.
identityRelation
Indicates that two entities are in fact the very same entity, not merely similar or equivalent.
-
B.
associatedWithAdministration
chosen
Indicates a relationship in which an entity is connected to, involved in, or under the responsibility of an administrative body, process, or function.
-
C.
reportsRelationship
Indicates that one entity formally provides information, findings, or status about another entity or situation.
-
D.
parentRelationship
Indicates a familial relationship in which one entity is the parent of another entity.
-
E.
laterRelationWith
Indicates that one entity stands in a temporal relationship to another such that it occurs or exists at a later time than the other.
- 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_69ca8318231881908fd1bc1c4d45d286 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe44815488190a912d63512e19af0 |
completed | March 31, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:09 p.m.