Triple
T8593532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Represents |
E203487
|
entity |
| Predicate | firstFormulated |
P78754
|
FINISHED |
| Object | February 2000 |
—
|
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: February 2000 | Statement: [Three Represents, firstFormulated, February 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFormulated Context triple: [Three Represents, firstFormulated, February 2000]
-
A.
firstDeveloped
chosen
Indicates that one entity was the earliest to create, originate, or bring another entity into existence.
-
B.
formulatedInYear
Indicates the specific calendar year in which something was originally created, devised, or formally established.
-
C.
hasFormulation
Indicates that one entity is expressed, prepared, or configured in a particular form or composition defined by another entity.
-
D.
independentlyFormulated
Indicates that multiple entities arrived at the same or similar idea, result, or formulation without influencing or relying on each other.
-
E.
formulatedInTermsOf
Indicates that one concept, statement, or representation is expressed, defined, or described using the language, framework, or components of another.
- 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_69ca832a7f108190b4e4f5648abf4aa2 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c5e8888190b721e791c449b0df |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.