Triple
T19078503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tower of Babel narrative |
E466962
|
entity |
| Predicate | languageBeforeEvent |
P28976
|
FINISHED |
| Object | one language |
—
|
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: one language | Statement: [Tower of Babel narrative, languageBeforeEvent, one language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageBeforeEvent Context triple: [Tower of Babel narrative, languageBeforeEvent, one language]
-
A.
languageOfEvent
Indicates the language in which an event is conducted, presented, or communicated.
-
B.
languageIntroduced
Indicates that a particular language was brought into use or made known within a certain context, time, or place.
-
C.
formerLanguage
chosen
Indicates that one entity was previously the language of another entity but is no longer in that role.
-
D.
heirBeforeEvent
Indicates that one entity is designated as the heir of another prior to a specified event occurring.
-
E.
languageShift
Indicates a change in the primary language used by an entity, such as switching from one language to another over time or in a given context.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e61b60819092d42614f04a087c |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.