Triple
T30007546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LBA |
E762364
|
entity |
| Predicate | advantageOverCHS |
P168807
|
FINISHED |
| Object | simplified addressing |
—
|
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: simplified addressing | Statement: [LBA, advantageOverCHS, simplified addressing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advantageOverCHS Context triple: [LBA, advantageOverCHS, simplified addressing]
-
A.
advantageOverEcho
Indicates that one entity possesses an advantage or superiority over another entity referred to as Echo.
-
B.
JapaneseAdvantage
Indicates that one party holds a comparative advantage or superior position specifically in a Japanese context (e.g., language, market, culture, or environment) relative to another.
-
C.
hasChineseVersion
Indicates that an entity has a corresponding version or representation available in Chinese.
-
D.
advantageOverHAM-6
Indicates that one entity has a comparative advantage or superiority over another entity in the context of HAM-6.
-
E.
advantageOverPhysical
Indicates that something possesses a benefit or superiority when compared to a physical or tangible counterpart.
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67953393481909fce15619f1a1c10 |
completed | May 2, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 29, 2026, 6:43 p.m.