Triple
T18656115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ngwee |
E456068
|
entity |
| Predicate | replacedSubunitName |
P23044
|
FINISHED |
| Object | pence |
—
|
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: pence | Statement: [ngwee, replacedSubunitName, pence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedSubunitName Context triple: [ngwee, replacedSubunitName, pence]
-
A.
hasSubunitName
Indicates that an entity includes or is associated with a named subunit or component as part of its structure or organization.
-
B.
replacementName
chosen
Indicates that one entity serves as a substitute or successor name for another entity, effectively replacing the original designation.
-
C.
replacedSubsystem
Indicates that one subsystem has been substituted or exchanged for another, taking over its role or function.
-
D.
replacedPartOf
Indicates that one entity has taken the place of another entity as a component or part within a larger whole.
-
E.
formerSubunit
Indicates that one entity was previously a subunit or subordinate part of another entity, but no longer holds that status.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55084ca3481909ff3fd9045f25dcd |
completed | April 19, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.