Triple
T22538681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrée de Jongh |
E557225
|
entity |
| Predicate | roleInCometLine |
P148583
|
FINISHED |
| Object | main organizer |
—
|
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: main organizer | Statement: [Andrée de Jongh, roleInCometLine, main organizer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCometLine Context triple: [Andrée de Jongh, roleInCometLine, main organizer]
-
A.
roleOnLine1
Indicates that an entity holds a specific role or function associated with the first line of a multi-line structure or sequence.
-
B.
roleInNebula
Indicates that an entity holds a specific function, position, or involvement within a particular nebula.
-
C.
roleInConstellation
Indicates the specific function or position an entity holds within a particular constellation.
-
D.
roleInProductLine
Indicates the specific functional or organizational role an entity holds within a particular product line.
-
E.
roleInApollo
Indicates that an entity holds or held a specific role or position within the Apollo program or an Apollo mission.
- 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_69e11e58662081909ae346ab384514ca |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f302cd4819098c97ca4fa96363e |
completed | April 29, 2026, 1:30 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:51 p.m.