Triple
T29760643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calypso |
E753757
|
entity |
| Predicate | conversionDesigner |
P175256
|
FINISHED |
| Object | Jacques Cousteau |
—
|
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: Jacques Cousteau | Statement: [Calypso, conversionDesigner, Jacques Cousteau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionDesigner Context triple: [Calypso, conversionDesigner, Jacques Cousteau]
-
A.
designConvertedTo
Indicates that one design has been transformed or translated into another design or format.
-
B.
reverseDesigner
Indicates that one entity is the designer or creator of another entity, with the direction of the relationship reversed from a primary “designer” predicate.
-
C.
conversionProcess
Indicates a process in which something is transformed or changed from one state, form, or representation into another.
-
D.
designCenter
Indicates that an entity serves as the primary location or hub where another entity is designed or conceptually developed.
-
E.
characterDesigner
Indicates a relationship where an entity is responsible for designing or creating the visual or conceptual characteristics of a character.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 28, 2026, 8:32 p.m.