Triple
T29016575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hedosophia |
E737323
|
entity |
| Predicate | roleInSPACs |
P197843
|
FINISHED |
| Object | SPAC sponsor |
—
|
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: SPAC sponsor | Statement: [Hedosophia, roleInSPACs, SPAC sponsor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSPACs Context triple: [Hedosophia, roleInSPACs, SPAC sponsor]
-
A.
roleInCosmos
Indicates the function, position, or significance an entity holds within the larger structure or order of the cosmos.
-
B.
roleInNebula
Indicates that an entity holds a specific function, position, or involvement within a particular nebula.
-
C.
roleInAddressing
Indicates the specific function or responsibility an entity has in dealing with or responding to a particular issue, situation, or task.
-
D.
roleInStellarFusion
Indicates the specific function or contribution an entity has within the processes that drive stellar nuclear fusion.
-
E.
roleInCouncil
Indicates that an entity holds a specific position or function within a council or governing body.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
| PDg | Predicate description generation | batch_69feb3419158819082f4666077535ca9 |
completed | May 9, 2026, 4:08 a.m. |
Created at: April 28, 2026, 9:46 a.m.