Triple
T5486244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GJ-3 |
E123587
|
entity |
| Predicate | languageOnPlate |
P4196
|
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: [GJ-3, languageOnPlate, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOnPlate Context triple: [GJ-3, languageOnPlate, English]
-
A.
languageOfLetters
Indicates that one entity is the language in which the other entity’s letters or written correspondence are composed.
-
B.
languageLabel
Indicates the human-readable name or label of a language associated with an entity or resource.
-
C.
languageOfSignage
chosen
Indicates the language used on signs or written displays associated with an entity.
-
D.
languageSpokenOnScreen
Indicates that a particular language is used in spoken dialogue or audible communication within an on-screen work (such as a film, show, or video).
-
E.
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.
- 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:10 p.m.