Triple
T30845679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parc de Marly |
E785624
|
entity |
| Predicate | hasRemnantOf |
P16216
|
FINISHED |
| Object | Château de Marly |
—
|
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: Château de Marly | Statement: [Parc de Marly, hasRemnantOf, Château de Marly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRemnantOf Context triple: [Parc de Marly, hasRemnantOf, Château de Marly]
-
A.
hasStructureRemnant
Indicates that an entity contains or includes a remaining part or leftover portion of a former structure.
-
B.
hasRemainsOf
chosen
Indicates that one entity physically contains, preserves, or is associated with the leftover physical traces or remnants of another entity.
-
C.
remnantDetected
Indicates that a remaining trace or leftover of a prior entity, event, or process has been identified.
-
D.
remnantUsedBy
Indicates that a remaining part or leftover of something is utilized or employed by another entity.
-
E.
isCandidateRemnantOf
Indicates that one entity is considered a possible remaining fragment or leftover part 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00b34364448190b8c9948d5a24d845 |
completed | May 10, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_6a00b2e4f13c819081bac7d763c414ad |
completed | May 10, 2026, 4:31 p.m. |
Created at: April 29, 2026, 8:46 p.m.