Triple
T7896979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boo |
E183362
|
entity |
| Predicate | roleInUnity |
P56496
|
FINISHED |
| Object | primary scripting option (historical) |
—
|
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: primary scripting option (historical) | Statement: [Boo, roleInUnity, primary scripting option (historical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInUnity Context triple: [Boo, roleInUnity, primary scripting option (historical)]
-
A.
roleInReact
Indicates that an entity participates in a reaction with a specified functional or contextual role (e.g., reactant, product, catalyst, or regulator).
-
B.
roleInNebula
Indicates that an entity holds a specific function, position, or involvement within a particular nebula.
-
C.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
-
D.
roleInCosmos
Indicates the function, position, or significance an entity holds within the larger structure or order of the cosmos.
-
E.
roleInIntegration
chosen
Indicates the specific function or responsibility an entity has within a combined or coordinated system, process, or integration.
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a187a0081909a0c0822c6dab1da |
completed | March 31, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:01 p.m.