Triple
T236297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cross of Saint George |
E4831
|
entity |
| Predicate | hasCharge |
P8394
|
FINISHED |
| Object | upright cross |
—
|
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: upright cross | Statement: [Cross of Saint George, hasCharge, upright cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharge Context triple: [Cross of Saint George, hasCharge, upright cross]
-
A.
hasElectricCharge
Indicates that an entity possesses a nonzero electric charge as a physical property.
-
B.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
-
C.
featuresCharge
Indicates that one entity includes, offers, or is characterized by a particular charge (such as a fee, cost, or pricing component).
-
D.
chargeOftenUsed
Indicates that an entity is frequently subjected to or associated with a particular charge (such as a legal, financial, or electrical charge).
-
E.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25ccab7648190be6e4f5febc1e313 |
completed | Feb. 28, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69a25b5dc640819092669575731c393f |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c2bda788190bcfc0bc94686f9e0 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.