Triple
T28610444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TCG |
E724155
|
entity |
| Predicate | translationMode |
P191345
|
FINISHED |
| Object | just-in-time compilation |
—
|
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: just-in-time compilation | Statement: [TCG, translationMode, just-in-time compilation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: translationMode Context triple: [TCG, translationMode, just-in-time compilation]
-
A.
translationMethod
Indicates the technique or process used to translate content from one language or form to another.
-
B.
translationDirection
Indicates the source and target languages involved in a translation, specifying the direction from the original language to the translated language.
-
C.
translationProperty
Indicates a relationship where one entity serves as a translated counterpart or translation-specific attribute of another entity.
-
D.
translationActivity
Indicates that an entity is engaged in the process of translating content from one language or form into another.
-
E.
textTranslation
Indicates a relationship where one text is rendered into another language or form while preserving its original meaning.
- F. None of above. chosen
Provenance (4 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: April 28, 2026, 4:29 a.m.