Triple
T4715485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Carlos, California |
E104625
|
entity |
| Predicate | hasBusinessSector |
P20603
|
FINISHED |
| Object | biotechnology companies |
—
|
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: biotechnology companies | Statement: [San Carlos, California, hasBusinessSector, biotechnology companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusinessSector Context triple: [San Carlos, California, hasBusinessSector, biotechnology companies]
-
A.
hasBusiness
Indicates that one entity owns, operates, or is formally associated with a business entity.
-
B.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
C.
hasIndustrialSector
chosen
Indicates that an entity is associated with, operates in, or belongs to a particular industrial sector or branch of economic activity.
-
D.
hasBusinessDivision
Indicates that an organization includes or is composed of a specific business division as a subordinate unit.
-
E.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
- 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_69bd43ec4a348190bc41afae43375e71 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.