Triple
T19215500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galápagos sea lion |
E480469
|
entity |
| Predicate | commonBehavior |
P7254
|
FINISHED |
| Object | basking on beaches |
—
|
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: basking on beaches | Statement: [Galápagos sea lion, commonBehavior, basking on beaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonBehavior Context triple: [Galápagos sea lion, commonBehavior, basking on beaches]
-
A.
commonAction
Indicates that multiple entities participate in or perform the same action or activity.
-
B.
commonOn
Indicates that two or more entities share the same location, context, or medium where they are present or occur together.
-
C.
commonIn
chosen
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
D.
defaultBehavior
Indicates the standard or fallback way an entity acts or responds when no specific or overriding instructions or conditions are provided.
-
E.
typicalInteraction
Indicates the usual or most common way in which two entities interact or relate to each other.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa3a417c819083e2e276d44d4d89 |
completed | April 20, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:22 p.m.