Triple
T18172999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plaxo |
E435077
|
entity |
| Predicate | Plaxo Pulse |
P130744
|
FINISHED |
| Object | social networking and activity feed service |
—
|
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: social networking and activity feed service | Statement: [Plaxo, Plaxo Pulse, social networking and activity feed service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Plaxo Pulse Context triple: [Plaxo, Plaxo Pulse, social networking and activity feed service]
-
A.
leadNation
Indicates that one entity holds the primary leadership role or governing authority over a nation.
-
B.
sapContains
Indicates that one entity spatially or logically contains another as a part, component, or subset within its bounds.
-
C.
cloudBased
Indicates that something is hosted, delivered, or operates via cloud computing infrastructure rather than on local hardware.
-
D.
FieldsightsMedium
Indicates a medium or channel through which information, observations, or data from field sites are communicated or presented.
-
E.
managementSoftware
Indicates that one entity is a software system used to organize, control, or coordinate the operations, resources, or processes of another entity.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df56d0a88190af3f407d2a3bb74f |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:30 a.m.