Triple
T16747077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSAP |
E406983
|
entity |
| Predicate | I/G bitMeaning |
P47684
|
FINISHED |
| Object | 0 indicates individual address |
—
|
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: 0 indicates individual address | Statement: [DSAP, I/G bitMeaning, 0 indicates individual address]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: I/G bitMeaning Context triple: [DSAP, I/G bitMeaning, 0 indicates individual address]
-
A.
letterMeaning
chosen
Indicates that a particular letter conveys a specific meaning, interpretation, or semantic content.
-
B.
stringMeaning
Indicates that one entity represents the semantic content or interpretation of a given string associated with another entity.
-
C.
lettersMeaning
Indicates that a set of letters or characters represents, signifies, or conveys a particular meaning or message.
-
D.
CISMeaning
Indicates that one concept, term, or symbol conveys, expresses, or stands for a particular meaning or interpretation in a given context.
-
E.
centralFormulaMeaning
Indicates that one formula or expression represents the primary or core meaning within a larger logical, mathematical, or semantic structure.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa2311748190a17416de577ad159 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.