Triple
T8542121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pula–thebe system |
E202221
|
entity |
| Predicate | subunitNameMeaning |
P83218
|
FINISHED |
| Object | shield |
—
|
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: shield | Statement: [pula–thebe system, subunitNameMeaning, shield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subunitNameMeaning Context triple: [pula–thebe system, subunitNameMeaning, shield]
-
A.
subunitSymbol
Indicates that one entity is the symbolic or abbreviated representation (symbol) of a subunit of another entity.
-
B.
subunitType
Indicates that one entity is a specific kind or classification of subunit within the structure or composition of another entity.
-
C.
hasSubunitName
Indicates that an entity includes or is associated with a named subunit or component as part of its structure or organization.
-
D.
subunitNamePlural
Indicates that an entity has multiple subunits and specifies the pluralized name used to refer collectively to those subunits.
-
E.
subunitOf
Indicates that one entity functions as a component or smaller part within the structure or organization of another, larger entity.
- 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_69ca832461e88190a654c5e44e233aa8 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6e26be48190b10bc62fad178dad |
completed | March 31, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:18 p.m.