Triple
T26331706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | phlogiston theory |
E662402
|
entity |
| Predicate | languageOfEarlyFormulations |
P61092
|
FINISHED |
| Object | Latin |
—
|
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: Latin | Statement: [phlogiston theory, languageOfEarlyFormulations, Latin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfEarlyFormulations Context triple: [phlogiston theory, languageOfEarlyFormulations, Latin]
-
A.
languageOfEarliestForm
Indicates the language in which the earliest known form or attested version of something (e.g., a text, name, or expression) is recorded.
-
B.
originalFormulationLanguage
chosen
Indicates the language in which something (such as a text, statement, or formulation) was originally created or expressed.
-
C.
languageOfEarlyServices
Indicates the language in which early services (such as initial or preliminary sessions, programs, or interventions) are conducted.
-
D.
languageOfFounders
Indicates the language or languages spoken or used by the founders of an entity.
-
E.
laterTraditionsLanguage
Indicates that later traditions or sources refer to or describe the subject using the specified language.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 26, 2026, 10:34 p.m.