Triple
T38387832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloches à travers les feuilles |
E899626
|
entity |
| Predicate | followedByInSet |
P194134
|
FINISHED |
| Object | Poissons d’or |
E899627
|
NE 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: Poissons d’or | Statement: [Cloches à travers les feuilles, followedByInSet, Poissons d’or]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByInSet Context triple: [Cloches à travers les feuilles, followedByInSet, Poissons d’or]
-
A.
followedByInSequence
Indicates that one event or element directly succeeds another in an ordered sequence.
-
B.
followedByInContext
chosen
Indicates that one element directly succeeds another within a specific contextual sequence or ordering.
-
C.
followedByClass
Indicates that one class or type is immediately succeeded by another class or type in a defined sequence or ordering.
-
D.
followedByComponent
Indicates that one component directly succeeds another component in a defined sequence or order.
-
E.
followsIn
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
- F. None of above.
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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffa9677be08190852c8ef6c2545fed |
completed | May 9, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41b2acf9f08190a8334729b9df8665 |
completed | June 28, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69ffa6570e2c8190a9d7b37f12b91d9a |
completed | May 9, 2026, 9:25 p.m. |
Created at: May 3, 2026, 4:31 p.m.