Triple
T18673636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eclipse (yacht) |
E456543
|
entity |
| Predicate | hasAntiPaparraziSystem |
P48202
|
FINISHED |
| Object | reported true |
—
|
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: reported true | Statement: [Eclipse (yacht), hasAntiPaparraziSystem, reported true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAntiPaparraziSystem Context triple: [Eclipse (yacht), hasAntiPaparraziSystem, reported true]
-
A.
defensiveSystem
chosen
Indicates a system or mechanism whose primary function is to protect, guard, or defend an entity against threats or attacks.
-
B.
isPartOfSystemProtecting
Indicates that one entity functions as a component within a larger system whose purpose is to provide protection.
-
C.
hasPASystem
Indicates that an entity possesses or is equipped with a public address (PA) system.
-
D.
hasDefenseStrategy
Indicates that an entity employs or is associated with a particular plan or set of measures designed to protect against threats or attacks.
-
E.
hasFacadeSystem
Indicates that one entity possesses or is equipped with a particular façade system as part of its structure or design.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556b41cd881908f37bf7c85e96559 |
completed | April 19, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.