Triple
T5737399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian passport |
E126531
|
entity |
| Predicate | languageInside |
P18209
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Indian passport, languageInside, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageInside Context triple: [Indian passport, languageInside, English]
-
A.
languageSpecifies
Indicates that one entity defines or constrains the syntax, semantics, or usage rules that govern how another language or linguistic system is expressed or interpreted.
-
B.
languageUse
chosen
Indicates the language or languages an entity uses for communication, expression, or interaction.
-
C.
languageIndependence
Indicates that a concept, method, or representation does not depend on any specific programming or natural language and can be applied uniformly across different languages.
-
D.
languageForm
Indicates the specific linguistic form or expression in which something is conveyed or represented.
-
E.
languageDesigned
Indicates that one entity created or developed the language used or associated with another entity.
- 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_69c0083082288190b7478cead6b5430a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0255c8c308190821f968ec41c5078 |
completed | March 22, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69c021c8195481909419808b002628aa |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:47 p.m.