Triple
T30943571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BB-28 |
E788324
|
entity |
| Predicate | equipmentOf |
P113532
|
FINISHED |
| Object | Sam Porter Bridges |
—
|
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: Sam Porter Bridges | Statement: [BB-28, equipmentOf, Sam Porter Bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equipmentOf Context triple: [BB-28, equipmentOf, Sam Porter Bridges]
-
A.
equippedFor
Indicates that one entity is suitably provided with the necessary tools, features, or capabilities to perform a particular function or handle a specific situation for another entity or purpose.
-
B.
equipmentIncludes
chosen
Indicates that one entity contains, comprises, or has as part of its set of items a specified piece or set of equipment.
-
C.
missionEquipment
Indicates that certain equipment is assigned to, used for, or associated with carrying out a specific mission.
-
D.
usesEquipment
Indicates that an entity employs or operates a particular piece of equipment to perform an action or fulfill a function.
-
E.
crewEquipment
Indicates that certain equipment is assigned to, used by, or associated with a specific crew.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:53 p.m.