Triple
T35481926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Celtigar |
E1025491
|
entity |
| Predicate | sigilFeature |
P132275
|
FINISHED |
| Object | crab |
—
|
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: crab | Statement: [House Celtigar, sigilFeature, crab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sigilFeature Context triple: [House Celtigar, sigilFeature, crab]
-
A.
signFeature
chosen
Indicates that an entity bears or displays a particular sign, symbol, or distinguishing feature.
-
B.
signatureFeature
Indicates that one entity is a defining or characteristic feature that distinctly identifies or typifies another entity.
-
C.
hasSiglum
Indicates that an entity is associated with a specific siglum, i.e., a standardized abbreviated symbol or code used to identify it.
-
D.
signatureVariant
Indicates that one signature is an alternative or modified form of another signature, differing in some aspect such as content, format, or representation while remaining related.
-
E.
inscriptionFeature
Indicates that one entity bears or contains an inscribed element or marking that is treated as a notable feature in relation to another entity.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.