Triple
T8418271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Jersey state seal |
E198782
|
entity |
| Predicate | LibertyHolds |
P82081
|
FINISHED |
| Object | staff with liberty cap |
—
|
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: staff with liberty cap | Statement: [New Jersey state seal, LibertyHolds, staff with liberty cap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LibertyHolds Context triple: [New Jersey state seal, LibertyHolds, staff with liberty cap]
-
A.
isUsuallyHeldBy
Indicates that something is most commonly or typically possessed, carried, or controlled by a particular entity.
-
B.
holdsHuck
Indicates that one entity is physically holding or carrying Huck.
-
C.
holdingType
Indicates the type or category of a holding or possession that one entity has in relation to another or to an asset.
-
D.
isStrategicAssetOf
Indicates that one entity is considered a strategically important resource or capability for another entity, contributing significantly to its long-term goals or competitive advantage.
-
E.
holdsIn
Indicates that a relationship, condition, or event is valid or occurs within a specified time interval or temporal context.
- 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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb84c7d6e48190a2bbde89c5d42af6 |
completed | March 31, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 6:06 p.m.