Triple
T5168879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admiralty anchor |
E116625
|
entity |
| Predicate | hasStockPosition |
P61919
|
FINISHED |
| Object | perpendicular to the plane of the arms |
—
|
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: perpendicular to the plane of the arms | Statement: [Admiralty anchor, hasStockPosition, perpendicular to the plane of the arms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStockPosition Context triple: [Admiralty anchor, hasStockPosition, perpendicular to the plane of the arms]
-
A.
hasBuildingStock
Indicates that an entity possesses or includes a collection or inventory of buildings.
-
B.
hasHolding
Indicates that one entity possesses, controls, or maintains ownership or custody of another entity as an asset or item.
-
C.
hasMarketStatus
Indicates the current commercial or trading condition of an entity, such as whether it is active, suspended, listed, or delisted in a market.
-
D.
hasPositionsFor
Indicates that one entity offers or contains available roles, jobs, or positions for another entity.
-
E.
marketPosition
Indicates the relative standing or rank an entity holds within a specific market compared to its competitors.
- 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_69bd445ff97c81909a2615cc56235470 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd794dd9988190922e138f2a9a3c62 |
completed | March 20, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd78d6a1388190804dcf568ca92129 |
completed | March 20, 2026, 4:41 p.m. |
Created at: March 20, 2026, 1:45 p.m.