Triple
T10435105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rex |
E246016
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Rexx |
E736221
|
NE 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: Rexx | Statement: [Rex, hasVariant, Rexx]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rexx Context triple: [Rex, hasVariant, Rexx]
-
A.
REXX
chosen
REXX is a high-level, easy-to-read scripting and macro language widely used on IBM mainframe systems for automation, data processing, and system control tasks.
-
B.
ARexx
ARexx is a REXX-based scripting language for the AmigaOS platform, commonly used to automate tasks and enable inter-application communication.
-
C.
Pear language
Pear language is an Austroasiatic language of the Pearic branch spoken by the Pear people of Cambodia and considered highly endangered.
-
D.
SNOBOL
SNOBOL is an early high-level programming language from the 1960s known for its powerful pattern-matching and string-processing capabilities.
-
E.
Caché
Caché is a tributary stream that feeds into the Bléone River in southeastern France.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea67344c81909984ab99b0ef1e64 |
completed | April 7, 2026, 11:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d87ec1a0908190b5369ad55cf2bcb1 |
completed | April 10, 2026, 4:38 a.m. |
Created at: April 6, 2026, 12:14 p.m.