Triple
T33634396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Howard, 14th Earl of Arundel |
E861650
|
entity |
| Predicate | collectionKnownAs |
P52939
|
FINISHED |
| Object | Arundel marbles |
—
|
NE NERFINISHED |
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: Arundel marbles | Statement: [Thomas Howard, 14th Earl of Arundel, collectionKnownAs, Arundel marbles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectionKnownAs Context triple: [Thomas Howard, 14th Earl of Arundel, collectionKnownAs, Arundel marbles]
-
A.
collectivelyKnownAs
chosen
Indicates that multiple entities are referred to together under a single shared name or designation.
-
B.
collectionKind
Indicates the type or category of collection to which an entity or group of entities belongs.
-
C.
collectionBuiltAround
Indicates that a collection is organized, structured, or conceptually centered around a particular core item, theme, or entity.
-
D.
knownForCollectionOf
Indicates that one entity is recognized or notable specifically for its collection or assemblage of another type of entity.
-
E.
collectionFeature
Indicates that a collection possesses or is characterized by a particular feature or attribute.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 1, 2026, 1:41 a.m.